Account Information Service Provider

Third-party service providers offer a number of financial services to end consumers. To provide such services, they require customer bank account information, such as primary account information, balances, transaction history, and beneficiary information. Third-party service providers require end-user consent to access account information.

The Temenos Digital mobile banking application supports third party application in receiving the account-sharing consent details from the same mobile device. After authentication, the customer can view the request details and approve or reject the consent. This solution is in adherence to the Berlin group standards (European open banking).

Following are the two consent types for sharing Account information:

• Global consent – TPP requests access to All eligible accounts and services for a user.
• Detailed Consent – TPP requests access to specific accounts and services, and the end user will provide the account details upon consent initiation at TPP. The relevant information for each account is listed.

The following sequence diagram explains the Open Banking AIS Consent flow integration work flow between a third party provider, Temenos Digital channel and the Transact core banking system.

The following sequence diagram explains the Open Banking AIS Consent flow integration work flow between a third party with the Saltedge gateway provider, Temenos Digital channel, and the Transact core banking system.

User Authorization

A third-party app redirects the users to the Temenos Digital banking app to authorize consent. Follow these steps to provide the authorization:

1. The user can see a page (configurable) showing information as an authorized third-party application to read your account information. Click Continue to proceed.
   
   
2. The user can view the Sign In page. Enter the credentials, Username and Password.
   
3. After Sign In, the user can view the list of accounts with the details to share with the third party provider. The user has the option to Approve or Reject the consent.     
   • In Global consent, the user cannot see what type of information is sharing, and in Detailed consent, the user can view the sharing information.
     

   

   

   

   

   • In Bank offered consent, user can select the accounts to share the information with the third-party provider. After selecting the account, the Approve option is enabled to the user.

   

   

   

   

   • If the user clicks Approve, the application displays an acknowledgment message: Your request was successful.

   

   

   

   

   

   

   •  If the user click Reject, the application displays an acknowledgment message: You have cancelled the consent request.

   

   

   

   

   

   When the user has installed and not logged into the online and mobile banking application, user will view the Terms and Conditions (Existing post login Terms and Conditions) acceptance on the login page.
   

Error Scenarios

The following are the error scenarios that may occur when the user is facing issues with the application:

• When the user does not have the permissions enabled in Spotlight application to approve or reject the consent.
  
• When the users account is not eligible as a part of the Open Banking eligibility check.
  
• When there is a server error where Digital application does not get a response from the back-end systems.
  

Spotlight Configurations

In Spotlight application -> Feature and Facilities, open banking access and open banking account consent details are defined.

The following features and actions are available in the Master data management level to manage or enable the Approve or Reject actions to the end users.

Fabric Configurations

The following Server and Client properties must be configured in the Fabric run time parameters.

Server Properties

Client Properties

Time Configuration

When redirecting from third party application to the banking application, the bank need to set the following configurations to show or hide the pre login info screen at the time of implementation.

An Identity service is being developed in Fabric to support the authentication of incoming request from TPP for Account details, transaction and beneficiary details to the core system. The core system can utilize this service to validate that the incoming request by TPP is from an authenticated online banking user. Post validation, the core system responds to TPP with the requested details. For more information on the Identity service, click here.

Manage Account Access

Once the user approves an account information consent via the Open banking flow, the user can view the Active consents provided in the Digital banking channel or mobile native application in Manage Account Access. For more information, see Manage Account Access.